Skip to content

TIKA-3133 - writeLimit and maxEmbeddedResources for recursive parsing - add header#326

Merged
tballison merged 1 commit intoapache:mainfrom
nddipiazza:TIKA-3133
Jul 15, 2020
Merged

TIKA-3133 - writeLimit and maxEmbeddedResources for recursive parsing - add header#326
tballison merged 1 commit intoapache:mainfrom
nddipiazza:TIKA-3133

Conversation

@nddipiazza
Copy link
Contributor

see https://issues.apache.org/jira/browse/TIKA-3133
and https://issues.apache.org/jira/browse/TIKA-3126

this will add new parameters to rmeta rest endpoint

writeLimit - max number of characters to store; if < 0, the handler will store all characters
maxEmbeddedResources - number of embedded resources that will be parsed. if < 0, it will handle unlimited embedded resources.

This will make it so we can control how many embedded docs will be parsed in a call to rmeta, and how many bytes will be written to the body.

@nddipiazza
Copy link
Contributor Author

@tballison i think this can be merged now. I disassociated it with TIKA-3126 so that this PR can be 100% focused on not hard coding those values.

@tballison tballison merged commit e2250e0 into apache:main Jul 15, 2020
tballison pushed a commit that referenced this pull request Jul 15, 2020
puthurr pushed a commit to puthurr/tika-fork that referenced this pull request Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments